The committers listed above are authorized under a signed CLA.

• ✅ login: chessman / name: Eugene Apollonsky (d3cc0a8)

Hi @chessman. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: chessman
Once this PR has been reviewed and has the lgtm label, please assign cpanato for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

✅ Deploy Preview for kubernetes-ingress-nginx canceled.

@chessman thanks for your contribution.

I would like to comment in a way that everyone gets on the same page.

• If a backend is in the same cluster as the ingress, the convention is to use service --type ClusterIP. But you are presenting a unconventional use-case that has no benefit for other community users of the controller. Summary of what you want is

  • first create a service --type NodePort in the same cluster as the ingress resource
  • then you want to configure the cluster internal dns name of the NodePort service, in the service.spec.externalName field, of another service of --type ExternalName, in the same cluster
  • then you want to configure a default-backend in a ingress, in the same cluster
  • and you want to use this service of --type ExternalName as the default-backend, also in the same cluster

• You must be having a valid reason, that is a requirement for you, for complicating matters like this But expecting a community project to change its code just because you want to use the controller in a non-conventional way, is not a fair or a reasonable expectation.

• You can fork the project and maintain your fork with the capability you are expecting. Its not possible for this project to triage, debug, identify, create & maintain new capabilities, using lua code, that only you need to use. The use of resources here will not be justified.

• The upstream K8S Ingress-API KEP defines specs and ingress-controllers implement the specs as per resources. But we are trying to get away from the Lua based implementations (of several features). We are also actually deprecating multiple currently stable features, that are popular, but have no future. This is because the available resources are required for security & Gateway-API.

Please wait and see if any other comments are made here or if a developer wants to triage, debug & work on this.

/retitle use a url outside the cluster as service type ExternalName for default-backend

/retitle use a NodePort service as ExternalName in another service type ExternalName for configuring default-backend

@longwuyuan

• No, my goal is to use a ClusterIP service in the same cluster but it is in another namespace.
• From my point of view, it is not a feature, it is a bug. The documentation says that default backend is a service. I don't see any mentions that it cannot be an external name. If a service used in Ingress can be, then why the default one cannot? The one-line fix is not in the lua part, so I guess it will work as long as you don't deprecate external services in Ingress.
• Currently Backend object is used for default backend with a wrong Service, so this code is incorrect regardless of whether you support this feature or not.

@chessman thanks for your comments. Using data to discuss helps everyone get on the same page.

• Use the data that you provided in the issue.

• As per the data in the issue you have the echo-service(default-backend) and the hello-app ingress in the same namespace(default)

• So you can just do kubectl expose deployment echo --port=8080 instead of creating service --type NodePort

• Then you can set the default backend in the ingress you showed there simply like this "nginx.ingress.kubernetes.io/default-backend: echo"

  • Note the the expose command without --name will create a service of --type ClusterIP with same name as deploment "echo"

• You also have options to set the global default-backend https://kubernetes.github.io/ingress-nginx/examples/customization/custom-errors/

@chessman Please continue discussion in the issue as its not a easy task to track issue discussions in multiple places

/ok-to-test
/triage accepted
/priority backlog

I'd like to test this locally and therefore

/hold

this PR for now.

@strongjz and @Gacko , its possible that this PR creates yet another CVE for the project.
A user can potentially configure a ingress to connect to a service in another namespace, and thus get past RBAC.

/kind bug